Proposed Idea: add session identifier #5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It's suitable for matching multiple DNS TAP messages to particular DNS resolution session.
|
Hi, Pavel: It looks like this would address the use case in #3. Did you happen to review the linked discussion? |
|
Hello! Any updates here? It would be nice to add these fields because it's important for us and we do not like the idea to use "our own" DNS TAP message format implementation. Also, I saw multiple requests about additional fields and it would be nice to add them all (especially for cache). |
|
Hi, Pavel: I would recommend bringing this up on the dnstap mailing list (http://lists.redbarn.org/mailman/listinfo/dnstap). There was an in-person meeting at DNS-OARC in Madrid last month among dnstap implementers and one of the topics raised was the process for adding additional fields to the current schema. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello!
As part of our DNS TAP experience it's very useful to have special field for matching multiple recursive DNS resolution requests into big one "resolution session" for analytics.
We started to use "extra" field for such purposes but I think it could be useful for standard to have session identifier also.